Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1285

reference
393-tree-1
name
1285
tree-preservation-order

undefined

393-tpo-1
uprn
address-text
point
POINT (-1.026515 50.884185)
geometry
MULTIPOLYGON (((-1.026445 50.884177,-1.026448 50.884191,-1.026458 50.884204,-1.026473 50.884214,-1.026493 50.884220,-1.026515 50.884223,-1.026537 50.884221,-1.026557 50.884214,-1.026573 50.884205,-1.026583 50.884192,-1.026587 50.884178,-1.026583 50.884164,-1.026574 50.884152,-1.026558 50.884142,-1.026538 50.884135,-1.026517 50.884133,-1.026495 50.884135,-1.026475 50.884141,-1.026459 50.884151,-1.026448 50.884163,-1.026445 50.884177)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL